• Seamlessly publish your app to the web from a Notebook environment.

• Develop in your favorite editor or notebook environment and seamlessly publish the result to the web.

Okay maybe add this part "seamlessly publish the result to the web." when there is clear documentation on how to do that :-)

I'm in doubt:

• Should "seamlessly publish the result to the web" be included?
• If yes. Should it be a separate bullet point?

Could you elaborate on why this is important to add to an already long list of items?

I think the ability to do that is important, and even fundamental for many use cases.

Publishing a development project as a webpage directly from your environment or Notebook without cumbersome deployment / conversion etc. etc. is (in my opinion) an important box to check for many users.

Together with the ability to then quickly iterate your development and immediately see the results in the webpage.

So there is a Notebook or other environment level where you can develop with other developers, and at the same time you have a (selective, constrained, polished) app that you serve from that environment to users.

So it enables an almost instant develop <-> web loop. Do others not also emphasize this? Like Gradio, etc.? Or the framework that mainly uses Plotly (is that Streamlit or another one?). I think it is an important part in many development cycles.

I think that part is pretty essential as a selling point, but would be good, but I don't know the user base well enough. Maybe others can chime in that have a good feel for the (potential) user base? @jbednar, any thoughts?

Conversely: are there also many cases where people do NOT need this in their project? So they stay entirely in a local environment / Notebook, and never need to pubish to a webpage?

Does it align with the roadmap? doc/about/roadmap.md

How-to guides provide step-by-step recipes for solving essential problems and tasks you encounter on a daily basis.

I would argue that a lot of the recipes are for solving tasks that arise for many people (not all) sometimes during their work.

For example advanced deployment or finetuning of the server is not something every one does and not daily.

I see your point. So maybe something like ... that arise when analyzing, visualizing and publishing data in a broad range of scenario's? Basically stating the main challenges Panel can help solve?

Lower down in the page it says this:

• If you're unsure, starting in a notebook is recommended as you familiarize yourself with Panel. However, you can switch between them at any time.

Suggested additional sentence: Hosted Notebook environements like https://ananconda.cloud and others are available for a quick start (or something similar).

Maybe. Can you explain why this is important?

If this should be included. It could be included in different places: Installation, core_concepts, its own guide(s) similar to the Deployment guides. What would be the best place to include this?

I think it's important (or at least relevant) because people might not be aware that this is an alternative to setting up and installing Jupyter from the ground up. That step can add al ot of friction for certain users in my view.

Hosted Notebooks allow them to skip that initially, and get to a working Panel example quickly, with as little friction as possible.

They can then always to choose to use the created .ipynb Notebook files in other (local) environments later.